Tyre physics just isn't ready. But I'm working on it.
The carcass works quite nicely and I'll be on the tread simulation soon.
Test Patch 0.6Q5 is now available with fixes and improvements!
Changes from 0.6Q3 to 0.6Q5 :
New map view for open configurations and track selection screen
Skid marks now remain when race restarts (excluding replays)
Skid marks are now visible on unmovable layout objects
FIX : Missing part of shadows at rear of LX4 and LX6
FIX : Shadows seen from a distance were not affected by haze effect
https://www.lfs.net/forum/thread/90208
Some other requests I still considering. Some requests, including the drift maximum lock increase, would cause an incompatibility issue. I do expect to release an incompatible version in the near future, so it looks like that should be possible, up to 45 degrees (no new tracks, cars or tyre physics in the incompatible version).
Changes from 0.6Q3 to 0.6Q5 :
New map view for open configurations and track selection screen
Skid marks now remain when race restarts (excluding replays)
Skid marks are now visible on unmovable layout objects
FIX : Missing part of shadows at rear of LX4 and LX6
FIX : Shadows seen from a distance were not affected by haze effect
https://www.lfs.net/forum/thread/90208
Some other requests I still considering. Some requests, including the drift maximum lock increase, would cause an incompatibility issue. I do expect to release an incompatible version in the near future, so it looks like that should be possible, up to 45 degrees (no new tracks, cars or tyre physics in the incompatible version).
I don't know if this can be done without messing up all the hotlaps for those cars. But as it seems so popular, I can look into it. If it would mess up the hotlaps then I won't do it, an increase in steering range would have to wait for the new tyre physics, which I have been working on.
But, to help me, can you tell me exactly which cars need more steering angle to help with drift and how much that extra angle should be? It really must remain within the realms of "realistic" and I guess that means it should not include any cars with front drive.
There is more to come. Explanation below.
At the moment the shadows do not affect transparency, and I didn't do anything to change that. It's a good point and I haven't even thought about that! I think with all the other things I am working on, the shadows on alpha surfaces will not be changed in this update.
The problem with skid marks on concrete is if the concrete object disappears, we could have floating skid marks. I haven't yet worked out a system to solve this. Though I haven't put much time into it. I suppose it's possible by registering every bit of skid on an object, so they can vanish if the object is deleted... again, probably not in this update.
I've been diverted onto some updates on the tyre physics, because I needed to send Eric an update with new editor functions, but the new tyre physics were in an "intermediate" state. Now I've brought them to a driveable state, I can update Eric's dev version and I can get back to some patch things.
But I don't want to try and say what else will be in the patch.
Yeah, normally the test patch threads are more lively and I keep adding more updates. This time, the shadows were tested, no serious bugs exist and then I've been diverted onto other things and there was also two weeks with the kids at home.
I'm back to work now so hopefully there should be more to test soon!
What are the things they are waiting for?
I don't follow all the discussions here, specially while I'm trying to focus on tyre physics, so I have probably missed things. But it would be good to know if InSim needs fixes or important updates.
That is such a ridiculous statement that you have simply made up in your mind and then decided to say it, without comparing it with any actual facts to check what you are saying.
If you want to make a point, you are welcome to do so, positive or negative. But if you want to state such negative viewpoints, you should support it with some kind of evidence. Otherwise you are just spreading the fantasy that exists in your mind.
If you look at the new version announcements over the past few years, you will see major improvements.
Bringing up the Scirocco is quite pathetic really. The one specific announcement in all the years we have been developing Live for Speed, that hasn't yet been released. You think it's sensible to attack us for it, several years later, because just once we believed we could release something, then later discovered the tyre physics weren't ready for it. You have so little to support the negative view you want to spread for your own amusement, that you come up with this worn out old beating stick that has been used against us for so many years and we have issued so many apologies about. All because of one medium powered front wheel drive car, that people have blown up into some kind of Holy Grail of sim racing.
I've been working mainly on the tyre physics.
Eric has been working on tracks.
Sorry but there's not much more to say at this point.
Anyway, here is a new compatible test patch with some small improvements. Most notably the car shadows are no longer cast towards the light. See the attached screenshot in the Test Patch 0.6Q3 thread.
https://www.lfs.net/forum/thread/90208
Eric has been working on tracks.
Sorry but there's not much more to say at this point.
Anyway, here is a new compatible test patch with some small improvements. Most notably the car shadows are no longer cast towards the light. See the attached screenshot in the Test Patch 0.6Q3 thread.
https://www.lfs.net/forum/thread/90208
Test Patch 0.6Q3 (now Q9)
WARNING : THIS IS A TEST
NOTE : THIS DOES NOT CONTAIN NEW TYRE PHYSICS OR ANY NEW CONTENT
PLEASE TEST BEFORE YOU POST
Hello Racers,
Here is a new TEST PATCH : 0.6Q9
This is only a minor update as I have mainly been working on the tyre physics.
There is an improvement in the car shadow system, which until now could cast shadows in the wrong direction.
Skid marks now remain remain when the race restarts and are visible on layout objects.
There is a new map view for open configurations and the track selection screen.
Please read the list of changes below for more information.
0.6Q9 is fully compatible with 0.6Q
- You can connect online with 0.6Q
- You can play replays from 0.6Q
You cannot upload hotlaps made with this test patch because it is only a test patch, not an official patch.
Please keep a backup of your LFS.exe from 0.6Q so you can easily go back if there are any problems.
Changes from 0.6Q7 to 0.6Q9 :
Small map opacity can now be set for light and dark map colours
Westhill paths adjusted and regenerated to avoid graphical holes
Autocross paths regenerated and physical hole fixed at skid pad
Changes from 0.6Q6 to 0.6Q7 :
Small map rotation enabled on new open configuration maps
Small map is now available on car park and autocross areas
Improvements on track selection screen using the area maps
Improved and cleaned up the Westhill, Rockingham, Kyoto maps
Changes from 0.6Q3 to 0.6Q6 :
New map view for open configurations and track selection screen
Skid marks now remain when race restarts (excluding replays)
Skid marks are now visible on unmovable layout objects
FIX : Missing part of shadows at rear of LX4 and LX6
FIX : Shadows seen from a distance were not affected by haze effect
Changes from 0.6Q to 0.6Q3 :
Shadows are no longer cast upwards or towards the light
Ambient (non-direct) shadow darkness now depends on distance
New text command /lang X to load language (data\language\X.txt)
Increased LOD distances of humans / drivers / marshalls
FIX : LFS could crash using /axload with a long layout name
FIX : Traffic lights did not work after texture resolution change
INSTALLATION INSTRUCTIONS :
A FULL version of LFS 0.6Q must already be installed
To install the PATCH using the SELF EXTRACTING ARCHIVE :
1) Move or save the patch into your main LFS folder
2) Double click the patch to extract it to that folder
3) When you see "Confirm File Replace" select "Yes to All"
4) Now you can start LFS in the normal way
NOTE : You can see if the patch is correctly installed when you run
the program (LFS.exe). At the bottom of the entry screen : 0.6Q9
DOWNLOADS :
PATCH 0.6Q TO 0.6Q9 (SELF EXTRACTING ARCHIVE) (if you already have 0.6Q) :
www.lfs.net/file_lfs.php?name=LFS_PATCH_6Q_TO_6Q9.exe (13 MB)
NOTE : THIS DOES NOT CONTAIN NEW TYRE PHYSICS OR ANY NEW CONTENT
PLEASE TEST BEFORE YOU POST
Hello Racers,
Here is a new TEST PATCH : 0.6Q9
This is only a minor update as I have mainly been working on the tyre physics.
There is an improvement in the car shadow system, which until now could cast shadows in the wrong direction.
Skid marks now remain remain when the race restarts and are visible on layout objects.
There is a new map view for open configurations and the track selection screen.
Please read the list of changes below for more information.
0.6Q9 is fully compatible with 0.6Q
- You can connect online with 0.6Q
- You can play replays from 0.6Q
You cannot upload hotlaps made with this test patch because it is only a test patch, not an official patch.
Please keep a backup of your LFS.exe from 0.6Q so you can easily go back if there are any problems.
Changes from 0.6Q7 to 0.6Q9 :
Small map opacity can now be set for light and dark map colours
Westhill paths adjusted and regenerated to avoid graphical holes
Autocross paths regenerated and physical hole fixed at skid pad
Changes from 0.6Q6 to 0.6Q7 :
Small map rotation enabled on new open configuration maps
Small map is now available on car park and autocross areas
Improvements on track selection screen using the area maps
Improved and cleaned up the Westhill, Rockingham, Kyoto maps
Changes from 0.6Q3 to 0.6Q6 :
New map view for open configurations and track selection screen
Skid marks now remain when race restarts (excluding replays)
Skid marks are now visible on unmovable layout objects
FIX : Missing part of shadows at rear of LX4 and LX6
FIX : Shadows seen from a distance were not affected by haze effect
Changes from 0.6Q to 0.6Q3 :
Shadows are no longer cast upwards or towards the light
Ambient (non-direct) shadow darkness now depends on distance
New text command /lang X to load language (data\language\X.txt)
Increased LOD distances of humans / drivers / marshalls
FIX : LFS could crash using /axload with a long layout name
FIX : Traffic lights did not work after texture resolution change
INSTALLATION INSTRUCTIONS :
A FULL version of LFS 0.6Q must already be installed
To install the PATCH using the SELF EXTRACTING ARCHIVE :
1) Move or save the patch into your main LFS folder
2) Double click the patch to extract it to that folder
3) When you see "Confirm File Replace" select "Yes to All"
4) Now you can start LFS in the normal way
NOTE : You can see if the patch is correctly installed when you run
the program (LFS.exe). At the bottom of the entry screen : 0.6Q9
DOWNLOADS :
PATCH 0.6Q TO 0.6Q9 (SELF EXTRACTING ARCHIVE) (if you already have 0.6Q) :
www.lfs.net/file_lfs.php?name=LFS_PATCH_6Q_TO_6Q9.exe (13 MB)
Last edited by Scawen, .
Thanks, everyone.
My thoughts are to get the tyre physics done without delays, without looking for perfection, just to get something out there that feels good and has a physical basis. The current public version tyre physics system uses some made-up force curves that are somewhat like real ones, and tuned to give reasonable output values, but they are not produced from an actual physical theory. The lateral and longitudinal forces are combined in a way that also is not based on physics, and was simply constructed to give a reasonable feeling.
In the new tyre physics, the forces are produced from code that follows physical laws, instead of looking up the forces from a curve. Lateral and longitudinal forces are output naturally, rather than being 'combined' in an arbitrary way.
There are assumptions involved, but they are 'known' assumptions that are there for a reason and can be improved upon in the future.
Anyway, I hope to continue with the work pace I have been doing in recent times, and don't see why this can't be the case.
My thoughts are to get the tyre physics done without delays, without looking for perfection, just to get something out there that feels good and has a physical basis. The current public version tyre physics system uses some made-up force curves that are somewhat like real ones, and tuned to give reasonable output values, but they are not produced from an actual physical theory. The lateral and longitudinal forces are combined in a way that also is not based on physics, and was simply constructed to give a reasonable feeling.
In the new tyre physics, the forces are produced from code that follows physical laws, instead of looking up the forces from a curve. Lateral and longitudinal forces are output naturally, rather than being 'combined' in an arbitrary way.
There are assumptions involved, but they are 'known' assumptions that are there for a reason and can be improved upon in the future.
Anyway, I hope to continue with the work pace I have been doing in recent times, and don't see why this can't be the case.
The cars were only one example. that's why I said "for example". For another example, the graphical systems need further updating before releasing public track editors. For example, I would prefer to have a new shadow system in place before releasing community editors that require community members to render their tracks using the outdated shadow rendering system. When the shadows are updated, tracks will need to be updated using the new shadow system.
Once again, it all comes back to the tyre physics, because after the tyre physics are completed, I can get back to the graphical updates.
There is no higher priority than the tyre physics. Remember, tyre physics... Scirocco... many years ago...
Once again, it all comes back to the tyre physics, because after the tyre physics are completed, I can get back to the graphical updates.
There is no higher priority than the tyre physics. Remember, tyre physics... Scirocco... many years ago...
I guess you are joking but, to make it quite clear anyway, I have to go through all cars reworking them after the tyre physics change. Basically giving them more realistic settings and design considerations to suit the more realistic physics.
The point is that if community made cars are available, it would be extremely difficult to rework 10,000 cars to remove all the bodges they have included to get around the flaws in the old physics.
There are so many reasons not to release community editors for an unfinished piece of software, I hope I don't need to explain it any more!
That is apart from the fact that updating editors and providing download services, compatibility checking, approval systems and so on will be many months of work, and as I keep saying, I don't want any more delays to the tyre physics.
The point is that if community made cars are available, it would be extremely difficult to rework 10,000 cars to remove all the bodges they have included to get around the flaws in the old physics.
There are so many reasons not to release community editors for an unfinished piece of software, I hope I don't need to explain it any more!
That is apart from the fact that updating editors and providing download services, compatibility checking, approval systems and so on will be many months of work, and as I keep saying, I don't want any more delays to the tyre physics.
We have always been interested in eventually releasing track and vehicle editors and we still hope to do so. But the idea has always beem to "finish" LFS first, and that means S3 license with some more default content and with updated tyre physics. For example, there is no point letting community members loose on developing cars, when the tyre physics would be changed significantly at some point.
I am interested to do this and it would be possible after the tyre physics is released. It is particularly difficult to do at the moment while there are two entirely separate branches of Live for Speed. It's a big task and not something I'd like to do twice.
As mentioned before, completing the tyre physics will allow many more possibilities for the future of LFS.
Banned cargame.nl for a month.
His previous post goes too far.
Better to have a break from here.
Meanwhile, I'm working on the tyre physics. The VR support really needed the 3D mirrors and that's why I did it. It really is the icing on the cake for VR support. Actually as I stated before there is something pretty bad about 2D mirrors in VR!
His previous post goes too far.
Better to have a break from here.
Meanwhile, I'm working on the tyre physics. The VR support really needed the 3D mirrors and that's why I did it. It really is the icing on the cake for VR support. Actually as I stated before there is something pretty bad about 2D mirrors in VR!
Yeah, we all know I need to get back on the tyre physics. I've started looking into that today, reading a few things, thinking how to start tackling the problems, seeing where I'm at, coming up with a plan of attack.
I think it's a case of coming in from two directions. One, looking in the code, making some notes, removing any code which is based on false assumptions, then coming up with good models to replace it. Two, at the same time, reading up on the elements that need to be modelled better. Plenty of testing all the way and extracting data to compare with real world data, and making sure everything scales nicely...
I will not try to aim for perfection. Far from it, the aim is to produce something that feels better to drive than the old tyre model for the sake of online racing. It will be a closer match with the behaviour of real world tyres, and will be based on reasonable assumptions and approximations, that can be improved upon in the future.
About the 0.6Q update. 3D mirrors were on my list for a long time. 2D mirrors really look quite bad in VR, as if there were LCD screens where your mirrors should be. Totally wrong. One day it just came to me how to do them. A half day experiment proved to me that the concept would work. As usual I thought it would all be done in a few days, but in fact was more like six weeks, with all the complications that came up and trying not to lose too much frame rate. I'm really happy with the result and LFS graphics came on a small step for everyone.
GamerMuscle has made a video featuring the new mirrors in LFS:
https://www.youtube.com/watch?v=wKBNfJFNkUY
I think it's a case of coming in from two directions. One, looking in the code, making some notes, removing any code which is based on false assumptions, then coming up with good models to replace it. Two, at the same time, reading up on the elements that need to be modelled better. Plenty of testing all the way and extracting data to compare with real world data, and making sure everything scales nicely...
I will not try to aim for perfection. Far from it, the aim is to produce something that feels better to drive than the old tyre model for the sake of online racing. It will be a closer match with the behaviour of real world tyres, and will be based on reasonable assumptions and approximations, that can be improved upon in the future.
About the 0.6Q update. 3D mirrors were on my list for a long time. 2D mirrors really look quite bad in VR, as if there were LCD screens where your mirrors should be. Totally wrong. One day it just came to me how to do them. A half day experiment proved to me that the concept would work. As usual I thought it would all be done in a few days, but in fact was more like six weeks, with all the complications that came up and trying not to lose too much frame rate. I'm really happy with the result and LFS graphics came on a small step for everyone.
GamerMuscle has made a video featuring the new mirrors in LFS:
https://www.youtube.com/watch?v=wKBNfJFNkUY
Last edited by Scawen, .
There are some complications with allowing virtual mirror at the same time as real mirrors in the new system. Mainly because it is no longer possible for them to use the same rendered image. The central mirror is narrower than a virtual mirror and its direction depends on the head position, so it is not compatible with the virtual mirror. A virtual mirror would have to be drawn as a separate image.
It's possible but not easy and I'm not really keen on doing it. I can't do it for this coming official version because I hope to release it very soon and get back to the tyre physics.
It's possible but not easy and I'm not really keen on doing it. I can't do it for this coming official version because I hope to release it very soon and get back to the tyre physics.
Test Patch 0.6P2 (now P9)
WARNING : THIS IS A TEST
NOTE : THIS DOES NOT CONTAIN NEW TYRE PHYSICS OR ANY NEW CONTENT
PLEASE TEST BEFORE YOU POST
PLEASE AVOID : OFF-TOPIC FEATURE REQUESTS / UNRELATED COMMENTS
Hello Racers,
Here is a new TEST PATCH : 0.6P9
- Realistic mirrors rendered from separate viewpoints
- Stereoscopic mirrors in VR and other 3D modes
- Controller improvements including a steering wheel turn limiter
- A new "walk" option for free view mode (SHIFT+U)
- Please read the change log below
0.6P9 is fully compatible with 0.6P
- You can connect online with 0.6P
- You can play replays from 0.6P
You cannot upload hotlaps made with this test patch because it is only a test patch, not an official patch.
Please keep a backup of your LFS.exe from 0.6P so you can easily go back if there are any problems.
Changes from 0.6P8 to 0.6P9 :
Mirrors :
Mirror offset sliders only shown if a car has an interior mirror
Graphics :
Improved detection of nearby objects that should be shadowed
Fixes :
Unassigned controls regained default key or button on restart
Changes from 0.6P7 to 0.6P8 :
Mirrors :
Increased resolution of mirror texture
Accurate view frustum for object culling in mirrors
Increased virtual mirror width from 0.3 to 0.333
Graphics :
Improved lighting on tyres and drivers - noticeable in dark places
Smoothed downward ambient lighting colour to avoid flickering
Misc :
New text command /horn X to set horn type (X = 1 to 5)
Fixes :
Your own car's shadow was not visible in the mirrors
Changes from 0.6P6 to 0.6P7 :
Mirrors :
Mirror adjustment and other view settings change with driver side
Reduced mirror up/down adjustment range to 20 degrees each way
Graphics :
Car shadow is now drawn when you are in an internal view
Fixes :
Mirror views could become corrupted when the car was damaged
Extreme adjustment of one mirror could corrupt other mirror views
Added checks to avoid a crash in LFS after a graphics driver error
Misc :
More translation updates - thank you translators
Changes from 0.6P5 to 0.6P6 :
Mirrors :
Increased vertical adjustment range for central mirror position
Added a "Default position" button to restore moved mirrors
Improved shape of interior mirror for XR road cars
Fixes :
Audio devices were sometimes displayed using the wrong code page
Misc :
Various translations updated - thank you translators
Changes from 0.6P4 to 0.6P5 :
Mirrors :
Adjustment values are now displayed and can be typed in
Additional translation strings for left and right mirrors
Fixes :
Objects could disappear with extreme up or down mirror adjustment
Changes from 0.6P3 to 0.6P4 :
Mirrors :
Mirror adjustment is now possible (in View Options)
Fixes :
Raceabout passenger seated positions were missing
Various steering animations included some unwanted leg movement
Internal mirror setting was overwritten by external setting on load
Helmet in mirror no longer moves with view when using a custom view
Changes from 0.6P2 to 0.6P3 :
Mirrors :
Mirrors are now realistic and include your own car in the image
A separate viewpoint is used to draw each mirror's view
Minor updates to some car models to improve visibility
Mirrors now use the same LOD setting as the main view
Virtual mirror is now available in follow view
VR :
Mirrors now use a full 3D view
Minor graphical updates :
Corrected downward ambient lighting colour (was too bright)
Slight reduction in near clipping plane distance
Multiplayer :
Increased UDP send buffer size from 12KB to 32KB
Changes from 0.6P to 0.6P2 :
Free view (SHIFT+U mode) :
Free view is now shown as an option in the Escape Menu
New walk mode which is good for wandering around in VR
Controllers :
Exit controller screen warning is not shown for real ESC key press
FF device is automatically assigned (if two or more are connected)
A single controller can now be selected (if two or more connected)
LFS tries to move force feedback wheel to centre when car is reset
Button and axis numbers now start at 1 (affects /button and /axis)
Assigned arrow keys work better (e.g. movement in free view mode)
Force feedback steering wheel turn limitation :
In your wheel settings use a large turn amount e.g. 900 degrees
In LFS Options - Controls set "Wheel turn" slider to match that
In LFS Options - Controls set "Wheel turn compensation" to 1.00
You should now find your wheel is correctly limited in all cars
VR :
Mouse look in free view mode in VR avoids pitch (stays horizontal)
Rift errors "display lost" and "HMD not present" shown as message
Misc :
You can now select a specific audio device in Audio Options screen
D3DCompiler_43.dll and D3DX9_43.dll are now supplied in dll folder
The card_cfg.txt file is no longer used - options moved to cfg.txt
INSTALLATION INSTRUCTIONS :
A FULL version of LFS 0.6P must already be installed
To install the PATCH using the SELF EXTRACTING ARCHIVE :
1) Move or save the patch into your main LFS folder
2) Double click the patch to extract it to that folder
3) When you see "Confirm File Replace" select "Yes to All"
4) Now you can start LFS in the normal way
NOTE : You can see if the patch is correctly installed when you run
the program (LFS.exe). At the bottom of the entry screen : 0.6P9
DOWNLOADS :
PATCH 0.6P TO 0.6P9 (SELF EXTRACTING ARCHIVE) (if you already have 0.6P) :
www.lfs.net/file_lfs.php?name=LFS_PATCH_6P_TO_6P9.exe (3.0 MB)
PATCH 0.6P TO 0.6P9 (ALTERNATIVE ZIP) (if you already have 0.6P) :
www.lfs.net/file_lfs.php?name=LFS_PATCH_6P_TO_6P9.zip (3.9 MB)
FOR HOSTING ONLY
DEDICATED HOST 0.6P9 (non-graphical version for hosting only) :
www.lfs.net/file_lfs.php?name=LFS_S3_DCON_6P9.zip (1.8 MB)
NOTE : THIS DOES NOT CONTAIN NEW TYRE PHYSICS OR ANY NEW CONTENT
PLEASE TEST BEFORE YOU POST
PLEASE AVOID : OFF-TOPIC FEATURE REQUESTS / UNRELATED COMMENTS
Hello Racers,
Here is a new TEST PATCH : 0.6P9
- Realistic mirrors rendered from separate viewpoints
- Stereoscopic mirrors in VR and other 3D modes
- Controller improvements including a steering wheel turn limiter
- A new "walk" option for free view mode (SHIFT+U)
- Please read the change log below
0.6P9 is fully compatible with 0.6P
- You can connect online with 0.6P
- You can play replays from 0.6P
You cannot upload hotlaps made with this test patch because it is only a test patch, not an official patch.
Please keep a backup of your LFS.exe from 0.6P so you can easily go back if there are any problems.
Changes from 0.6P8 to 0.6P9 :
Mirrors :
Mirror offset sliders only shown if a car has an interior mirror
Graphics :
Improved detection of nearby objects that should be shadowed
Fixes :
Unassigned controls regained default key or button on restart
Changes from 0.6P7 to 0.6P8 :
Mirrors :
Increased resolution of mirror texture
Accurate view frustum for object culling in mirrors
Increased virtual mirror width from 0.3 to 0.333
Graphics :
Improved lighting on tyres and drivers - noticeable in dark places
Smoothed downward ambient lighting colour to avoid flickering
Misc :
New text command /horn X to set horn type (X = 1 to 5)
Fixes :
Your own car's shadow was not visible in the mirrors
Changes from 0.6P6 to 0.6P7 :
Mirrors :
Mirror adjustment and other view settings change with driver side
Reduced mirror up/down adjustment range to 20 degrees each way
Graphics :
Car shadow is now drawn when you are in an internal view
Fixes :
Mirror views could become corrupted when the car was damaged
Extreme adjustment of one mirror could corrupt other mirror views
Added checks to avoid a crash in LFS after a graphics driver error
Misc :
More translation updates - thank you translators
Changes from 0.6P5 to 0.6P6 :
Mirrors :
Increased vertical adjustment range for central mirror position
Added a "Default position" button to restore moved mirrors
Improved shape of interior mirror for XR road cars
Fixes :
Audio devices were sometimes displayed using the wrong code page
Misc :
Various translations updated - thank you translators
Changes from 0.6P4 to 0.6P5 :
Mirrors :
Adjustment values are now displayed and can be typed in
Additional translation strings for left and right mirrors
Fixes :
Objects could disappear with extreme up or down mirror adjustment
Changes from 0.6P3 to 0.6P4 :
Mirrors :
Mirror adjustment is now possible (in View Options)
Fixes :
Raceabout passenger seated positions were missing
Various steering animations included some unwanted leg movement
Internal mirror setting was overwritten by external setting on load
Helmet in mirror no longer moves with view when using a custom view
Changes from 0.6P2 to 0.6P3 :
Mirrors :
Mirrors are now realistic and include your own car in the image
A separate viewpoint is used to draw each mirror's view
Minor updates to some car models to improve visibility
Mirrors now use the same LOD setting as the main view
Virtual mirror is now available in follow view
VR :
Mirrors now use a full 3D view
Minor graphical updates :
Corrected downward ambient lighting colour (was too bright)
Slight reduction in near clipping plane distance
Multiplayer :
Increased UDP send buffer size from 12KB to 32KB
Changes from 0.6P to 0.6P2 :
Free view (SHIFT+U mode) :
Free view is now shown as an option in the Escape Menu
New walk mode which is good for wandering around in VR
Controllers :
Exit controller screen warning is not shown for real ESC key press
FF device is automatically assigned (if two or more are connected)
A single controller can now be selected (if two or more connected)
LFS tries to move force feedback wheel to centre when car is reset
Button and axis numbers now start at 1 (affects /button and /axis)
Assigned arrow keys work better (e.g. movement in free view mode)
Force feedback steering wheel turn limitation :
In your wheel settings use a large turn amount e.g. 900 degrees
In LFS Options - Controls set "Wheel turn" slider to match that
In LFS Options - Controls set "Wheel turn compensation" to 1.00
You should now find your wheel is correctly limited in all cars
VR :
Mouse look in free view mode in VR avoids pitch (stays horizontal)
Rift errors "display lost" and "HMD not present" shown as message
Misc :
You can now select a specific audio device in Audio Options screen
D3DCompiler_43.dll and D3DX9_43.dll are now supplied in dll folder
The card_cfg.txt file is no longer used - options moved to cfg.txt
INSTALLATION INSTRUCTIONS :
A FULL version of LFS 0.6P must already be installed
To install the PATCH using the SELF EXTRACTING ARCHIVE :
1) Move or save the patch into your main LFS folder
2) Double click the patch to extract it to that folder
3) When you see "Confirm File Replace" select "Yes to All"
4) Now you can start LFS in the normal way
NOTE : You can see if the patch is correctly installed when you run
the program (LFS.exe). At the bottom of the entry screen : 0.6P9
DOWNLOADS :
PATCH 0.6P TO 0.6P9 (SELF EXTRACTING ARCHIVE) (if you already have 0.6P) :
www.lfs.net/file_lfs.php?name=LFS_PATCH_6P_TO_6P9.exe (3.0 MB)
PATCH 0.6P TO 0.6P9 (ALTERNATIVE ZIP) (if you already have 0.6P) :
www.lfs.net/file_lfs.php?name=LFS_PATCH_6P_TO_6P9.zip (3.9 MB)
FOR HOSTING ONLY
DEDICATED HOST 0.6P9 (non-graphical version for hosting only) :
www.lfs.net/file_lfs.php?name=LFS_S3_DCON_6P9.zip (1.8 MB)
Last edited by Scawen, .
Reason : 0.6P9
No problem, sometimes I find a break is needed then getting back into work with a few useful features is a good start. As you know, I want to get some serious progress done on the tyre physics as it will allow a lot of possibilities for LFS in the future.
I don't see a "nearly dead" community. Obviously there is less activity than there was in the past, but death isn't the word that springs to mind if you actually look at what's going on. Looking at the lfsworld graphs there is still an *average* of around 150 *licensed* people online at any time and the number of licensed people online often goes above 250. Yeah, quite a few of these are drifting or cruising but there is racing going on every day, if you choose to join a server.
We are not lacking in motivation. Actually work has picked up a lot since those quiet years and I see a good future in LFS. I work at a more sustainable rate and also have a hobby and a family, so that's quite balanced really.
I believe that the things we add to LFS in the future will be good fun and there will be ups and downs in the online activity.
Yes, we announced it but did not release it because we didn't like the way the car had to be set up. It showed up flaws in the tyre physics. I went into a massive push to sort out the tyre physics but it turned out more difficult the more I found out about it as the months went by. That time was also at the end of a period of many years of very hard work. We also moved house to a different part of the country after our children were born and work ended up slowing, except for vital updates.
Eventually I got into cross country cycling and stopped smoking which is good because I am healthier and will hopefully live longer. The VR support was a boost for us and now I'm well beyond stage 1 of my cycling hobby. I'm able to work a lot and still do a few rides each week. I've been trying to get this stage of VR development sorted so I can get back to the tyre physics which will allow more types of vehicle to be simulated.
EDIT: Removed the final part, the explanation is above. We made some decisions that weren't the best but I believe we are getting back on track. The new tyre physics will really help, along with new content.
Eventually I got into cross country cycling and stopped smoking which is good because I am healthier and will hopefully live longer. The VR support was a boost for us and now I'm well beyond stage 1 of my cycling hobby. I'm able to work a lot and still do a few rides each week. I've been trying to get this stage of VR development sorted so I can get back to the tyre physics which will allow more types of vehicle to be simulated.
EDIT: Removed the final part, the explanation is above. We made some decisions that weren't the best but I believe we are getting back on track. The new tyre physics will really help, along with new content.
Last edited by Scawen, .
Obviously I agree it is a pity there isn't more choice of licensed racing servers at the moment. We are working hard on things to improve the situation. We're beyond that slow period we went through a few years ago. I'm sure the new track and tyre physics will help, and some new types of vehicle, though these are still some months away. I've been trying to make sure LFS is the best VR sim racing experience to get some more people in that way.
One thing though, people could help by actually going online. I see a LOT of people saying, this would be fun if only there were people to race with. Well... guess who can do something about that?
It's no good looking at the list of hosts then not joining. Instead, pick one and go there, even if it's empty. At least one person has to join or it obviously will be empty! The next person who comes along might just join you. 
One thing though, people could help by actually going online. I see a LOT of people saying, this would be fun if only there were people to race with. Well... guess who can do something about that?
It's no good looking at the list of hosts then not joining. Instead, pick one and go there, even if it's empty. At least one person has to join or it obviously will be empty! The next person who comes along might just join you. Thank you for the test and feedback.
I was a bit confused at first but I think you mean when I get stuck into the tyre physics again?
Thanks for your suggestions. I'll pass them through my mind but I don't really expect to dive deep into controller support at this time.
I am not sure why your XBox one controller doesn't have separate axes. Mine (a wireless one that came with the Rift engineering sample) does have separate axes, just using the Microsoft auto-installed driver. I'm not sure how I can distinguish between the two. Does yours report only 5 axes? Mine reports 6.
Thank you for this test. Actually I got that inverse setting from your original post (see below) also stated by K0Z3L_43V3R, though I think he was doing a copy / paste + edit of yours.
I'll set invert to 0 for the next update.I guess you got the L and R the wrong way round. Anyway, LFS now reports the correct axis names and you should see those triggers with Z axis now, instead of RY (LFS displayed wrongly all these years).
No, I'm just doing a bit more on VR then back to the tyre physics. Meanwhile, Eric is working on a new track. No time estimates for these.
EDIT: but -> bit - thanks loopingz
EDIT: but -> bit - thanks loopingz
Last edited by Scawen, .
Test Patch 0.6N7
EDIT : Official Version 0.6P is now available!
https://www.lfs.net/patch-6p
WARNING : THIS IS A TEST
NOTE : THIS DOES NOT CONTAIN NEW TYRE PHYSICS OR ANY NEW CONTENT
PLEASE TEST BEFORE YOU POST
PLEASE AVOID : OFF-TOPIC FEATURE REQUESTS / UNRELATED COMMENTS
Hello Racers,
Here is a new TEST PATCH : 0.6N7
- Support for the new Oculus 1.3 software and Rift CV1
- OpenVR support updated to 0.9.19
- Various improvements to controller support (see below)
0.6N7 is fully compatible with 0.6N
- You can connect online with 0.6N
- You can play replays from 0.6N
You cannot upload hotlaps made with this test patch because it is only a test patch, not an official patch.
Please keep a backup of your LFS.exe from 0.6N so you can easily go back if there are any problems.
Changes from 0.6N6 to 0.6N7 :
Translations :
Many translations updated. Thank you translators!
VR :
Default HUD field of view is now 70 degrees / HUD distance 0.5m
Improved centralisation of one-eye monitor view on desktop window
Auto-updater is avoided in VR mode and helpful options are offered
Crosshairs are always visible when watching a training replay
Changes from 0.6N4 to 0.6N6 :
VR :
Fixed an error in calculation of Rift's vertical FOV
The intro replay is avoided if LFS is started in VR mode
LFS now pauses and hides crosshairs when Rift focus is lost
OpenVR support updated to 0.9.19
Controllers :
RGT wheel should now be identified as a Thrustmaster
Misc :
Added left and right arrows to the "Look function" option
Music in setup screens is no longer enabled by default
Changes from 0.6N3 to 0.6N4 :
Controllers :
Controllers with 5 axes now default to combined brake / throttle
Combined brake / throttle axis now defaults to correct direction
Automatically set Clutch setting to axis if wheel has clutch pedal
Automatic preset is now attempted on first of multiple controllers
Controller screen in game now shows correct pedals and steer gauge
New joystick look mode using two axes to control look direction
Arrow keys can now be assigned to wheel buttons (default D-pad)
Default 900 degrees turn for Logitech G25 / G27 / Driving Force
Attempted reasonable presets for Thrustmaster and DFGT wheels
A scroll bar appears if there are more than 16 available axes
Removed axis calibration system that had various problems
You can now type in the active range of an axis function
Typed range can exceed input range to reduce axis effect
Look Roll axis function now has a full 360 degree range
Changes from 0.6N2 to 0.6N3 :
VR :
Rift headphones are now used for sound output (default setting)
Rift remote can now be used for click / escape / virtual keyboard
Improved appearance of top row (ESC / F keys) of virtual keyboard
Controllers :
Controllers may now be plugged in and detected after LFS is started
Refresh button to detect controllers in Options - Controls screen
Controllers are now sorted (not dependent on order of connection)
Separate controller type setting for with / without controllers
Automatic controls assignment for various game controllers
Warning when you press ESC to exit controller setup screen
Button functions are now easier to see when in car
Fixes :
Axis names were previously displayed wrongly in Options - Controls
It was possible to enter a state where chat box could not be opened
Changes from 0.6N to 0.6N2 :
VR :
New LFSRiftVR DLL supports Oculus 1.3 software
IPD slider movement is now detected and message displayed
Now correctly handles CV1's different up and down FOV values
User can now cause LFS to exit through the Oculus software
INSTALLATION INSTRUCTIONS :
A FULL version of LFS 0.6N must already be installed
To install the PATCH using the SELF EXTRACTING ARCHIVE :
1) Move or save the patch into your main LFS folder
2) Double click the patch to extract it to that folder
3) When you see "Confirm File Replace" select "Yes to All"
4) Now you can start LFS in the normal way
NOTE : You can see if the patch is correctly installed when you run
the program (LFS.exe). At the bottom of the entry screen : 0.6N7
DOWNLOADS :
EDIT : Official Version 0.6P is now available!
https://www.lfs.net/patch-6p
PATCH 0.6N TO 0.6N7 (SELF EXTRACTING ARCHIVE) (if you already have 0.6N) :
www.lfs.net/file_lfs.php?name=LFS_PATCH_6N_TO_6N7.exe (1.3 MB)
PATCH 0.6N TO 0.6N7 (ALTERNATIVE ZIP) (if you already have 0.6N) :
www.lfs.net/file_lfs.php?name=LFS_PATCH_6N_TO_6N7.zip (1.6 MB)
https://www.lfs.net/patch-6p
WARNING : THIS IS A TEST
NOTE : THIS DOES NOT CONTAIN NEW TYRE PHYSICS OR ANY NEW CONTENT
PLEASE TEST BEFORE YOU POST
PLEASE AVOID : OFF-TOPIC FEATURE REQUESTS / UNRELATED COMMENTS
Hello Racers,
Here is a new TEST PATCH : 0.6N7
- Support for the new Oculus 1.3 software and Rift CV1
- OpenVR support updated to 0.9.19
- Various improvements to controller support (see below)
0.6N7 is fully compatible with 0.6N
- You can connect online with 0.6N
- You can play replays from 0.6N
You cannot upload hotlaps made with this test patch because it is only a test patch, not an official patch.
Please keep a backup of your LFS.exe from 0.6N so you can easily go back if there are any problems.
Changes from 0.6N6 to 0.6N7 :
Translations :
Many translations updated. Thank you translators!
VR :
Default HUD field of view is now 70 degrees / HUD distance 0.5m
Improved centralisation of one-eye monitor view on desktop window
Auto-updater is avoided in VR mode and helpful options are offered
Crosshairs are always visible when watching a training replay
Changes from 0.6N4 to 0.6N6 :
VR :
Fixed an error in calculation of Rift's vertical FOV
The intro replay is avoided if LFS is started in VR mode
LFS now pauses and hides crosshairs when Rift focus is lost
OpenVR support updated to 0.9.19
Controllers :
RGT wheel should now be identified as a Thrustmaster
Misc :
Added left and right arrows to the "Look function" option
Music in setup screens is no longer enabled by default
Changes from 0.6N3 to 0.6N4 :
Controllers :
Controllers with 5 axes now default to combined brake / throttle
Combined brake / throttle axis now defaults to correct direction
Automatically set Clutch setting to axis if wheel has clutch pedal
Automatic preset is now attempted on first of multiple controllers
Controller screen in game now shows correct pedals and steer gauge
New joystick look mode using two axes to control look direction
Arrow keys can now be assigned to wheel buttons (default D-pad)
Default 900 degrees turn for Logitech G25 / G27 / Driving Force
Attempted reasonable presets for Thrustmaster and DFGT wheels
A scroll bar appears if there are more than 16 available axes
Removed axis calibration system that had various problems
You can now type in the active range of an axis function
Typed range can exceed input range to reduce axis effect
Look Roll axis function now has a full 360 degree range
Changes from 0.6N2 to 0.6N3 :
VR :
Rift headphones are now used for sound output (default setting)
Rift remote can now be used for click / escape / virtual keyboard
Improved appearance of top row (ESC / F keys) of virtual keyboard
Controllers :
Controllers may now be plugged in and detected after LFS is started
Refresh button to detect controllers in Options - Controls screen
Controllers are now sorted (not dependent on order of connection)
Separate controller type setting for with / without controllers
Automatic controls assignment for various game controllers
Warning when you press ESC to exit controller setup screen
Button functions are now easier to see when in car
Fixes :
Axis names were previously displayed wrongly in Options - Controls
It was possible to enter a state where chat box could not be opened
Changes from 0.6N to 0.6N2 :
VR :
New LFSRiftVR DLL supports Oculus 1.3 software
IPD slider movement is now detected and message displayed
Now correctly handles CV1's different up and down FOV values
User can now cause LFS to exit through the Oculus software
INSTALLATION INSTRUCTIONS :
A FULL version of LFS 0.6N must already be installed
To install the PATCH using the SELF EXTRACTING ARCHIVE :
1) Move or save the patch into your main LFS folder
2) Double click the patch to extract it to that folder
3) When you see "Confirm File Replace" select "Yes to All"
4) Now you can start LFS in the normal way
NOTE : You can see if the patch is correctly installed when you run
the program (LFS.exe). At the bottom of the entry screen : 0.6N7
DOWNLOADS :
EDIT : Official Version 0.6P is now available!
https://www.lfs.net/patch-6p
PATCH 0.6N TO 0.6N7 (SELF EXTRACTING ARCHIVE) (if you already have 0.6N) :
www.lfs.net/file_lfs.php?name=LFS_PATCH_6N_TO_6N7.exe (1.3 MB)
PATCH 0.6N TO 0.6N7 (ALTERNATIVE ZIP) (if you already have 0.6N) :
www.lfs.net/file_lfs.php?name=LFS_PATCH_6N_TO_6N7.zip (1.6 MB)
Last edited by Scawen, .
Yes, the best way to do that is have graphics and physics on two different threads, so more CPU power is available for each of them (assuming the CPU has more than 1 core). The physics system must then store interpolatable snapshots of completed physics steps, for the graphics thread to render whenever it is ready.
It's a good system but requires a large overhaul of the program, on the graphics and physics sides. That is fine but, as I keep saying, it's far too difficult to do while I still have two separate versions of LFS, the development version and the public version. This is one of the reasons why the tyre physics is my top priority (after getting past this important month or two for VR). When it is done, we go back to having a single version of LFS. Also it will allow new types of vehicle and so on.
It's a good system but requires a large overhaul of the program, on the graphics and physics sides. That is fine but, as I keep saying, it's far too difficult to do while I still have two separate versions of LFS, the development version and the public version. This is one of the reasons why the tyre physics is my top priority (after getting past this important month or two for VR). When it is done, we go back to having a single version of LFS. Also it will allow new types of vehicle and so on.
It does actually but the problem is that the physics updates at 100 Hz.
So between some graphics updates you have 1 physics step and between others you have 2.
So I think, each second, you see 25 of these:
1, 1, 2
Your eyes / brain can see this irregularity which happens in a 25 Hz cycle. You can also see this on an ordinary monitor if you enable vertical sync and look sideways.
So between some graphics updates you have 1 physics step and between others you have 2.
So I think, each second, you see 25 of these:
1, 1, 2
Your eyes / brain can see this irregularity which happens in a 25 Hz cycle. You can also see this on an ordinary monitor if you enable vertical sync and look sideways.
Ah, that is the old problem with the headset having 75 Hz frame rate, while LFS has a 100 Hz physics update rate. Nothing we can do about that in the near future (eventually I'd like to do physics and graphics on separate threads and that would be part of the solution). Unfortunately the Vive and Rift customer versions have 90 Hz frame rate, so this problem still exists. It would have been great if they could run at 100 Hz!
Thanks, I've fixed them now.
I am interested in this but can't do it now. The main complication is the reverse direction text and I still need to research and code for this. But I must keep it lower priority than the tyre physics.
Does that work correctly in the LFS virtual keyboard? LFS calls Windows functions that should be handling all these character conversions.
FGED GREDG RDFGDR GSFDG